CCCCOOOONNNNFFFFIIIIGGGGUUUURRRRAAAATTTTIIIIOOOONNNN FFFFIIIILLLLEEEESSSS describes how to change a literal view into a
dynamic view.
When replaying an archive, you can only show views for metrics
contained in the archive. For this purpose, there are ppppmmmmllllooooggggggggeeeerrrr(1)
configuration files for the pre-defined views in the files
////vvvvaaaarrrr////ppppccccpppp////ccccoooonnnnffffiiiigggg////ppppmmmmllllooooggggggggeeeerrrr////ccccoooonnnnffffiiiigggg....vvvviiiieeeewwww....****. To create an archive
containing the metrics required to display any of the pre-defined
xxxxrrrrttttGGGGrrrraaaapppphhhhFFFFoooorrrreeeeggggrrrroooouuuunnnnddddCCCCoooolllloooorrrr and xxxxrrrrttttHHHHeeeeaaaaddddeeeerrrrFFFFoooorrrreeeeggggrrrroooouuuunnnnddddCCCCoooolllloooorrrr default to
xxxxrrrrttttFFFFoooorrrreeeeggggrrrroooouuuunnnnddddCCCCoooolllloooorrrr if not specified (likewise for the background
colors). Also see ppppmmmmDDDDeeeeffffaaaauuuullllttttCCCCoooolllloooorrrrssss above.
The default values for these resources (as specified in
////uuuussssrrrr////lllliiiibbbb////XXXX11111111////aaaapppppppp----ddddeeeeffffaaaauuuullllttttssss////PPPPmmmmCCCChhhhaaaarrrrtttt) defines the width and height of each
dialog, but the X and Y positions are not specified - hence dialogs use
interactive placement by default, unless the _d_e_s_k_t_o_p(1) has been
configured for random window placement. Consult the XXXX(1) man page for
The parser implements a simple grammar as follows; keywords are shown
literally, variables are enclosed in angle brackets and optional syntax
is enclosed in square brackets. Ellipsis denotes repetition. Blank
lines and lines starting with #### are ignored. A new line is expected
between each CCCChhhhaaaarrrrtttt and between each PPPPllllooootttt. Case is not significant for
keywords.
# comment
Version <number> [host dynamic|literal]
Scheme <schemename> color color ...
Scheme ...
Chart Style <style> [Scale from <min> to <max>] [Legend off]
Plot Color <color> Host <host> Metric <metric> [Instance <instance>]
Plot Color <color> Host <host> Metric <metric> [Matching <regex>]
Plot ...
Chart ...
Each line starting with SSSScccchhhheeeemmmmeeee specifies a list of colors comprising the
color scheme named <_s_c_h_e_m_e_n_a_m_e>. The default color scheme is named #-
_c_y_c_l_e, and is predefined using an XXXX(1) resource (see the ppppmmmmDDDDeeeeffffaaaauuuullllttttCCCCoooolllloooorrrrssss
application resource or the ----ddddcccc command line argument). A color scheme
declaration extends to the end of the line.
Each line starting with CCCChhhhaaaarrrrtttt creates a new chart containing the plots
specified on each subsequent line starting with PPPPllllooootttt. If the SSSSccccaaaalllleeee for a
chart is not specified, then the chart will use auto-scaling. <_s_t_y_l_e>
must be one of ppppllllooootttt, aaaarrrreeeeaaaa, bbbbaaaarrrr, ssssttttaaaacccckkkkiiiinnnngggg or uuuuttttiiiilllliiiizzzzaaaattttiiiioooonnnn. The LLLLeeeeggggeeeennnndddd is
on (i.e. shown) by default. <_c_o_l_o_r_s> are specified in the standard XXXX(1)
syntax; e.g. ####rrrrrrrrggggggggbbbbbbbb where the red, green and blue components are two
digit hex numbers, or the XXXX(1) color database names may also be used. As
a special case, if a previously defined color scheme name is used, then
the color for the plot will be the next unused color from the that color
scheme. Color scheme names take precedence over color names, so care is
required not to use names for color schemes which clash with names in the
color name database. If all colors in the color scheme have been used,
then the list is recycled.
Metrics which have a singular instance domain should not specify an
instance. If an IIIInnnnssssttttaaaannnncccceeee is given, the <_i_n_s_t_a_n_c_e> name extends to the
end of the line (i.e. spaces are allowed, but <_i_n_s_t_a_n_c_e> should not be
quoted). If there are multiple instances of the same metric, separate
PPPPllllooootttt specifications may be given in order to create plots of only
specific instances. Alternatively, if the IIIInnnnssssttttaaaannnncccceeee keyword is missing
and the metric does not have a singular instance domain (i.e. there may
be multiple instances), then a plot is created for every instance. If
the keyword MMMMaaaattttcccchhhhiiiinnnngggg is used (instead of IIIInnnnssssttttaaaannnncccceeee), then plots will be
created for all instances which have instance names that match the
supplied regular expression pattern, <_r_e_g_e_x>. See rrrreeeeggggeeeexxxx(3G) for details
about regular expressions. Lines which are likely to create multiple
plots from the one PPPPllllooootttt specification would normally use a color scheme
for <_c_o_l_o_r> so that each plot is created with a different color.
Finally, there should be exactly one line starting with VVVVeeeerrrrssssiiiioooonnnn. If
<_n_u_m_b_e_r> is 1111....1111 (or later), then the hhhhoooosssstttt ddddyyyynnnnaaaammmmiiiicccc and hhhhoooosssstttt lllliiiitttteeeerrrraaaallll syntax
is parsed (in version 1111....0000 this syntax is ignored). The default is hhhhoooosssstttt
lllliiiitttteeeerrrraaaallll, meaning when this configuration file is loaded as a View, the
<_h_o_s_t> specifies the actual host for each plot. If the configuration
file is hhhhoooosssstttt ddddyyyynnnnaaaammmmiiiicccc, then the <_h_o_s_t> specified for each plot is ignored,
instead being replaced by the current host in the View Selection dialog